AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAA LEGAL RIGHTS AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ============================================================================= IMPORTANT: READ BEFORE INSTALLING OR USING THIS SOFTWARE ============================================================================= You should carefully read the following terms and the terms set forth in the NOTICES especially those under the headings "No Warranty", "Limitation of Liability" and "US Government Legends", before using the software programs ("Software") and any documentation you have obtained from 3Com. Installation or use of the Software indicates that you accept such terms. NO WARRANTY =========== THE SOFTWARE AND DOCUMENTATION ARE PROVIDED ON AN "AS IS" BASIS AND ALL RISK IS WITH YOU. BECAUSE THE SOFTWARE AND DOCUMENTATION ARE PROVIDED TO YOU FREE OF CHARGE, 3COM MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO ANY MATTER WHATSOEVER. IN PARTICULAR, ANY AND ALL WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT OF THIRD PARTIES RIGHTS ARE EXPRESSLY EXCLUDED. FURTHER, 3COM MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE SOFTWARE AND DOCUMENTATION PROVIDED YOU ARE FREE OF ERRORS OR VIRUSES OR THAT THE SOFTWARE AND DOCUMENTATION ARE SUITABLE FOR YOUR INTENDED USE. Some states do not allow the exclusion of implied warranties or the limitation of incidental or consequential damages for consumer products, so the above limitations and exclusions may not apply to you. This warranty gives you specific legal rights which may vary from state to state. LIMITATION OF LIABILITY ======================= IN NO EVENT SHALL 3COM OR ITS SUPPLIERS BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES, LOSS OF DATA OR DATA BEING RENDERED INACCURATE, LOSS OF PROFITS OR REVENUE, OR INTERRUPTION OF BUSINESS IN ANY WAY ARISING OUT OF OR RELATED TO THE USE OR INABILITY TO USE THE SOFTWARE AND/OR DOCUMENTATION, REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT, (INCLUDING NEGLIGENCE), STRICT PRODUCT LIABILITY OR OTHERWISE, EVEN IF ANY REPRESENTATIVE OF 3COM OR ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states do not allow the exclusion of implied warranties or the limitation of incidental or consequential damages for consumer products, so the above limitations and exclusions may not apply to you. This warranty gives you specific legal rights which may vary from state to state. US GOVERNMENT LEGENDS ===================== If you are a government agency, then this software and documentation is provided to you subject to the following restricted rights: For units of the Department of Defense: Restricted Rights Legend: Use, duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software Clause at 48 C.F.R. 52.227-7013. 3Com Ireland, c/o 3Com Limited, ISOLAN House, Brindley Way, London Road, Hemel Hempstead, Hertfordshire, HP3 9XJ, England. For civilian agencies: Restricted Rights Legend: Use, reproduction or disclosure is subject to restrictions set forth in subparagraph (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 48 C.F.R. 52.227-19 and the limitations set forth in 3Com's standard commercial agreement for the Software. Unpublished rights reserved under the copyright laws of the United States. FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFF HOW TO USE THE TFTP SERVER FFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF =============================== CONTENTS =============================== F1 : PC Requirements F2 : Supported Adapter Cards F3 : Files on the Install Disk F4 : Installation and Configuration F5 : Operation of the TFTP Server F6 : Packet Drivers F7 : TokenLink III (R) 16/4 Packet Driver F8 : Configuring Supported Cards F9 : Configuring Unsupported Cards F10: CUSTOM.EXE F11: Possible Problems F12: Target Directory and File Structure F13: De-Installation F14: IP Address F15: Default Gateway IP Address F16: Sub-Net Mask F17: Simple Example F1: PC REQUIREMENTS =================== The package is designed to operate on DOS-based PCs, running as a standalone program. A minimum of 640Kbytes of memory, a floppy disk drive, a hard disk and a network adapter card is required. At least 2.5 Mbytes of hard disk space is required for the installed program. MS-DOS (R) version 5.x or greater is required. F2: SUPPORTED ADAPTER CARDS ============================ The package supports the following 3Com network adapter cards: - EtherLink II (R) 3C503 - EtherLink II TP 3C503B-TP - EtherLink II/16 3C503-16 - EtherLink III 3C509 - EtherLink III TP 3C509-TP - EtherLink/MC 3C523B - EtherLink/MC TP 3C533B-TP - TokenLink(R) III 16/4 3C619 (see `TokenLink III 16/4 Packet Driver' below) - Other (see `Configuring Non-Supported Cards' below) XT (R), AT (R) and MCA (R) PCs and clones are supported. However, XT PCs will only support 8 bit cards. F3: FILES ON THE INSTALL DISK ============================= The following files are present on your install disk :- INSTALL.EXE - the program that will install the software TFTPFLS.EXE - a self extracting file that contains the TFTP software README - documentation on the Management Agent software 3COMTFTP.TXT - this file DEINSTAL.EXE - the utility which removes all installed files F4: INSTALLATION AND CONFIGURATION ================================== The installation utility creates a directory structure on the hard disk of the target machine. It also modifies config.sys and autoexec.bat as required. The original versions of these files are retained so that the software may be de-installed. NOTE If you are installing TokenLink III 16/4 , you must first install IBM Lan Support. The installation process for the default configurations of the supported network adapter cards is as follows: * Insert the diskette in the drive A:. * At the A: prompt, type install. * Follow the screen prompts for the parameters you must enter or confirm. These are: 1/ the IP address for the TFTP server 2/ the default gateway (router) IP address (optional - see below) 3/ and the sub-net mask. (a mask is generated automatically, but you may change it). These will be saved, along with other data, in the NETDEV.SYS file (see below). When all the selections have been made, the files will be expanded into appropriate directories. When you are offered the choice of how to handle your system files, we recommend you opt for creating minimum config.sys and autoexec.bat files. The other choices require editing of these files. * When the installation is complete, you will be instructed to reboot the PC. During the reboot, the system will pause. At this point, press CTRL C to abort or any other key to invoke the server. Once the computer has been re-booted, you must check for the correct MAC address (if it is FFFFFFFFFFFF, refer to the Problem section below), and look for other error messages. If clear and correct, the TFTP server is ready to download a new software image. Should you wish to employ a non-default configuration, refer to H: below. For information on how to use non-supported adapter cards, refer to F9: below. F5: OPERATION OF THE TFTP SERVER ================================ The TFTP server is designed for unattended operation. As part of the installation process the installed software modifies the config.sys and autoexec.bat files to load the server components and automatically start-up the server. The server listens for incoming TFTP transfer requests. The server will answer requests sequentially, not in parallel. Simultaneous download is not possible. It is not available for any other application. The TFTP Server supports the NETASCII mode of transfer only. Consult your 3Com managed device's User Guide for details of how to initiate the download process. It is essential that you have set the device's IP address before you attempt to download. You must enter a filename, a server IP address and a destination (target device). When a TFTP request is received, the server will validate the filename and attempt to locate the file in one of the transfer directories. Once initiated, the server provides you with information about the status of the download. You can cancel the server by pressing 'q'. This returns you to normal DOS operation. Re-invoke the server using TFTP_S.EXE in the \3COMTFTP\EXE directory. F6: PACKET DRIVER ================= Each network adapter card requires a packet driver. The packet driver is a device driver or TSR that conforms to a specific software interface. Each type of card installed needs a separate packet driver. For the supported 3Com cards, packet drivers are supplied with the software. The installation program will automatically set up the packet driver based on the information you have provided during installation. If you have a non-3Com or unsupported 3Com network adapter card, you can normally obtain Public Domain packet drivers to drive your card. These are not directly supported by the installation program. Load your packet driver to the \3COMTFTP\EXE directory. Refer to the section on unsupported cards below. The 3Com packet drivers are provided under the terms of the GNU General Licence Agreement (a copy of which is held on this disk in \3COMTFTP\NOTICES). These packet drivers and the associated source code are held on this disk in \3COMTFTP\EXE. F7: TOKENLINK III 16/4 PACKET DRIVER ==================================== The Token Ring packet driver IBMTOKEN is an Ethernet packet driver. The IBM Lan Support program must be installed before it can be used. The TokenLink Adapter must be used with default settings. The Token Ring packet driver is provided under the terms of the GNU General Licence Agreement (a copy of which is held on this disk in \3COMTFTP\NOTICES). The source code of this Token Ring packet driver is held on this disk in \3COMTFTP\EXE. F8: CONFIGURING SUPPORTED CARDS =============================== The standard configurations are designed to use the factory defaults for a particular card. If you use a standard configuration, you will not have to adjust the jumpers and switch settings on the card. Standard configurations are available for all of the supported cards: refer to the manual which came with the card. You can use the 3Com EtherDisk (R), which comes with your card, to display the required data. If you use a non-standard configuration, you will be asked during the installation to provide the details of the settings on the card. Use the EtherDisk, which comes with your card, to display the required data. F9: CONFIGURING UNSUPPORTED CARDS ================================= Use the installation process to select a card type of `Other'. This results in a line being added to your autoexec.bat file. You must edit the autoexec.bat file using a DOS editor. Change the line \3COMTFTP\EXE\rem replacing `rem' with the name of the packet driver for your card and the appropriate settings. The settings that are needed by the packet driver can be found by typing the name of the packet driver without any settings. Make a note of the settings that are required and enter appropriate values in the autoexec.bat file. Hexadecimal values are entered in the form 0xN, where N is the hex number. The usual settings are:- Software Interrupt - 0x7e (this is the default value). Hardware Interrupt - 0-15 (set on card: ensure that this does not clash with any other devices). Port I/O - 0xN (a three digit hex number, usually between 200 and 3E0). Cable Type - N (this is usually a flag; 1 for the normal connection or 0 for AUI). An example of a packet driver set is - 3C503 0x7e 3 0x300 1 | | | | | | | | | Cable type | | | Port I/O | | Hardware Interrupt | Software Interrupt Packet Driver name If you have installed the server on drive C, the line in your autoexec.bat file will read : C:\3COMTFTP\EXE\3C503 0x7e 3 0x300 1 Copy the packet driver for your card into the directory 3COMTFTP\EXE. Ensure that NETDEV.SYS has been entered into your config.sys file as: DEVICE=C:\3COMTFTP\EXE\NETDEV.SYS where C is the drive that the server has been installed on. Your machine must be rebooted for these changes to take effect. F10: CUSTOM.EXE =============== The custom.exe program, located in 3COMTFTP\EXE, is used to set-up the IP address, default gateway, and sub-net mask for the server. The Install program uses this to set-up your system with the values you enter. You can, if you wish, use custom.exe directly. If you are going to run this program, you should backup the netdev.sys file before proceeding. To invoke the program change directory to \3COMTFTP\EXE and type custom netdev.sys. You will be presented with a menu driven interface which you can use to change various settings. The most common settings you may wish to change are in the 'site customization' menu. It is here that you can set-up the IP address, default gateway and sub-net mask. You can give a name to the server by which it can be identified. You can also use this program to check the TFTP server IP settings. The changes will be saved to the netdev.sys file which is loaded by config.sys file when the machine is booted. F11: POSSIBLE PROBLEMS ====================== If, when you reboot your PC, an Ethernet address of FFFFFFFFFFFF is displayed, or the server software does not load at all, your card has not been found. Possible causes are:- 1) Problem: An incorrect value has been entered for the packet driver. Action: Check that the settings on your card agree with the values you have entered for the packet driver. You can do this by looking at the physical card or by running the set-up utility that came with your card. 2) Problem: The packet driver is conflicting with another piece of software. Action: If another network package is running on your PC, disable it and try running the server again. You should not try and run two network applications through the same card. 3) Problem: The card is conflicting with another piece of hardware. Action: Check the interrupt that you have set on the card is not the same as any other piece of hardware. A usual value that is OK is 10, though this is only a guide. The first request by a device to initiate a download (the client) may result in the error message, TFTP: ERROR FROM FOREIGN HOST ABORTED BY CLIENT REQUEST appearing, followed a few seconds later by a second request. This is normal operation and shows the client validating the first block of data received, before updating its non-volatile memory. F12: DE-INSTALLATION ==================== A utility is provided to allow you to de-install the package from the hard disk. The actions of this utility will be to restore your original config.sys and autoexec.bat files and delete all server executable and data files from the hard disk. F13: TARGET DIRECTORY AND FILE STRUCTURE ======================================== The installation creates a directory on the target machine called 3COMTFTP. The following sub-directories will be created also: \3COMTFTP\EXE \3COMTFTP\BACKUP \3COMTFTP\xxx The directory, \3COMTFTP\EXE, is used to hold the TFTP server program (TFTP_S.EXE), the customised configuration file, NETDEV.SYS, and the packet drivers (3C5??.COM) needed for the supported network adapter cards. The directory, \3COMTFTP\BACKUP, contains the original config.sys and autoexec.bat files. The directories, \3COMTFTP\xxx, are used to hold the Management Agent Images for the various managed devices. F14: IP ADDRESS =============== The TFTP server uses the Internet protocol. In this protocol every host machine must have a unique Internet protocol address (IP address). If your PC is already connected to a network, you should consult with your network administrator who will be able to give you a suitable address. If your site supports a number of sub-networks separated by IP routers, you will need to configure the default gateway address. IP addresses are 32 bit numbers which are usually written down in the so-called 'dot' or 'dotted quad' notation. This consists of four numbers separated by dots (for example: 123.45.67.8). Each number should be in the range 0-255, although in practice the values 0 and 255 have special meanings. You should take great care to ensure that you do not use an IP address that is already used (or visible) on your network. For this reason we can not supply the server with a default IP address. You MUST enter a value for this field. Consult your network administrator. F15: DEFAULT GATEWAY IP ADDRESS =============================== If the Hub you wish to serve is not on the same IP network or sub-network as your own, you will need to access it via a gateway. If you use a gateway, you must enter the IP address of the GATEWAY in this field. If you do not use a gateway, leave this field as 0.0.0.0 F16: SUB-NET MASK ================= A Sub-Net Mask is calculated automatically by the server, based on the IP address you entered. The calculated value will be inserted for you. This may need to be changed depending on the addressing scheme in use on your network. Consult your network administrator. If the server and device are on the same IP network, ensure that the sub-net mask of the device you are upgrading is the same as the server mask. F17: SIMPLE EXAMPLE =================== If your network does not use Internet Protocol, you may use a simple point-to-point connection such as the suggested set-up below. The IP addresses cited are only examples to show the format. Whatever IP parameters you use, you MUST either: a) de-install the server software, or b) reset the parameters to null (0.0.0.0) IMMEDIATELY after the download. TFTP server<------------------------------------->LinkBuilder Device 192.168.100.1 IP Address 192.168.100.n 0.0.0.0 Default Gateway/Router IP Address 0.0.0.0 255.255.0.0 Sub-Net Mask 255.255.0.0* * On the LinkBuilder FMS, this should be entered in hexadecimal notation, i.e.: FFFF0000. In the above diagram, n is a number between 2 and 254, and is unique for the each LinkBuilder Unit on the network. If you have any doubt at all, consult your network administrator. ________________________________________________________________________________ (R) means a registered trademark. (TM) means a trademark. 3Com, LinkBuilder, EtherDisk, Etherlink and TokenLink are registered trademarks, and MSH a trademark, of 3Com Corporation. Other trademarks are the property of their respective owners. Document Number: DRA1850-0AAA04 Revision: 00 Issued: 1 April 1996 Copyright 1995,1996 3Com Ireland.